John Daughtry
John M. Carroll
Abstract
An NSF sponsored workshop on Creativity and Rationale in Software Design was held at University Park, PA in June, 2008. The participants represented the spectrum of software design, which was reflected in the discussions. This report summarizes the workshop with respect to the discipline of software engineering.
- Aurisicchio M., M. Gourtovaia, R. Bracewell, and K. Wallace (2008): How to Evaluate Reading and Interpretation of Differently Structured Engineering Design Rationales, Artificial Intelligence in Engineering Design, Analysis, and Manufacturing, 22(4), 345--358. Google Scholar
Digital Library
- Buckingham Shum, S., and N. Hammond (1994): Argumentationbased Design Rationale: What Use at What Cost? International Journal of Human-Computer Studies, 40(4), 603--652. Google ScholarDigital Library
- Burge, J. (2008): Researching Under Uncertainty, Artificial Intelligence in Engineering Design, Analysis, and Manufacturing, 22 (4), 311--324. Google ScholarDigital Library
- Burge, J., J. Carroll, R. McCall, and I. Mistrik. (2008): Rationale-Based Software Engineering. Heidelberg: Springer-Verlag. Google ScholarDigital Library
- Carroll, J., and M. Rosson, (1992): Getting Around the Task-Artifact Cycle: How to Make Claims and Design by Scenario. ACM Trans. Inf. Syst. 10(2), 181--212. Google ScholarDigital Library
- Carroll, J. and P.A. Swatman, (2002): Structured-case: A Methodological Framework for Building Theory in Information Systems Research, European Journal of Information Systems, 9: 235--242. Google ScholarDigital Library
- Haynes, S.R. (2006): Three Studies of Design Rationale as Explanation. In Rationale Management in Software Engineering (Du-toit, A., McCall, R., Mistrik, I., & and Paech B., Eds.), Heidelberg: Springer-Verlag, pp. 53--71.Google Scholar
- Koestler, A. (1964): The Act of Creation, New York: Macmillan.Google Scholar
- Kunz, W., H. Rittel, (1970): Issues as Elements of Information Systems. Working Paper 131, Center for Urban and Regional Development, University of California, Berkeley.Google Scholar
- Sjøberg, D., T. Dybå, B. Anda, and J. Hannay. (2008): Building Theories in Software Engineering. Guide to Advanced Empirical Software Engineering (Eds. Forrest Shull, Janice Singer, and Dag I.K. Sjøberg). Heidelberg: Springer-Verlag, 312--336.Google Scholar
Index Terms
- Creativity and rationale in software design
Recommendations
Scientific design rationale
Design rationale should be regarded both as a tool for the practice of design, and as a method to enable the science of design. Design rationale answers questions about why a given design takes the form that it does. Answers to these why questions ...
Design thinking and creativity of colocated versus globally distributed software developers
AbstractDesigning software is an activity in which software developers think and make design decisions that shape the structure and behavior of software products. Designing software is one of the least understood software engineering activities. In a ...
The software design activities of six teams of developers (three colocated and three distributed) are observed and analyzed. Considering Design Thinking, more problem‐space exploration is observed in colocated teams. Furthermore, connection issues and ...
Design rationale: Researching under uncertainty
Rationale research in software development is a challenging area because although there is no shortage of advocates for its value, there is also no shortage of reasons for why rationale is unlikely to be captured in practice. Despite more than 30 years ...
Comments